Skip to content

Document method comment style - #12338

Open
mhlidd wants to merge 1 commit into
masterfrom
matthew.li/agents-javadoc-comments
Open

Document method comment style#12338
mhlidd wants to merge 1 commit into
masterfrom
matthew.li/agents-javadoc-comments

Conversation

@mhlidd

@mhlidd mhlidd commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

What Does This Do

Adds an agent code convention requiring concise Javadoc comments for documentation that applies to an entire method, rather than line comments or plain block comments.

Motivation

Keeps method-level documentation discoverable through Java tooling while preventing verbose comments from obscuring the implementation.

Additional Notes

This is an instruction-only change with no runtime impact.

Contributor Checklist

Jira ticket: N/A

@mhlidd mhlidd added type: documentation comp: tooling Build & Tooling tag: ai generated Largely based on code generated by an AI or LLM labels Aug 28, 2026
@mhlidd
mhlidd marked this pull request as ready for review August 28, 2026 21:46
@mhlidd
mhlidd requested a review from a team as a code owner August 28, 2026 21:46
@mhlidd
mhlidd requested review from ygree and removed request for a team August 28, 2026 21:46

@datadog-datadog-prod-us1 datadog-datadog-prod-us1 Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Datadog Autotest: PASS

More details

The new rule applies only to agent instructions. It does not change runtime code.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Datadog Autotest · Commit cbc899f · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest

@dd-octo-sts

dd-octo-sts Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite Status
Startup 🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results
Scenario Candidate master Δ (95% CI of mean)
startup:insecure-bank:iast:Agent 14.85 s 14.73 s [-0.1%; +1.7%] (no difference)
startup:insecure-bank:tracing:Agent 13.59 s 13.69 s [-1.5%; +0.1%] (no difference)
startup:petclinic:appsec:Agent 17.41 s 16.87 s [-1.4%; +7.8%] (no difference)
startup:petclinic:iast:Agent 17.40 s 17.52 s [-1.6%; +0.2%] (no difference)
startup:petclinic:profiling:Agent 17.36 s 16.68 s [-1.6%; +9.8%] (unstable)
startup:petclinic:sca:Agent 17.30 s 17.18 s [-0.1%; +1.6%] (no difference)
startup:petclinic:tracing:Agent 16.69 s 16.57 s [-0.4%; +1.8%] (no difference)

Commit: cbc899fa · CI Pipeline · Benchmarking Platform UI


Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp: tooling Build & Tooling tag: ai generated Largely based on code generated by an AI or LLM type: documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant